Can be a good use case for @deprecate. it would require moving the implementation to the new name and marking the old name with it.

Can be a good use case for @deprecate. it would require moving the implementation to the new name and marking the old name with it.

The main reason why I haven't marked like that yet is because it may trigger a lot of depwarn messages right? Also, we cannot just use @deprecate because it will break specializations of make_tracer and traced_type_inner. We agreed to put these names and finally rename everything on the 0.3 release.

As of Julia 1.5, functions defined by @deprecate do not print warning when julia is run without the --depwarn=yes flag set, as the default value of --depwarn option is no. The warnings are printed from tests run by Pkg.test().

this is the current state of things